CLP-1110 Rerun dependent test suites when shared code and fixtures change - #211

Part of CLP-910.

A test suite that does not run when its dependencies change is not much better
than one that cannot fail. Several suites here exercise shared/ and
test-fixtures/jira/, but their triggers only watch their own action directory,
so a change to the shared code did not rerun them.

shared/** was watched by one suite out of seven

These all import jira_common or path_utils, and none of them listed
shared/**:

• test-create-jira-release-ticket
• test-create-jira-version
• test-get-jira-release-notes
• test-release-jira-version
• test-resolve-ktlo-epic
• test-update-release-ticket-status

Only test-create-integration-ticket had it. Added to both the pull_request
and push filters of the other six.

The KTLO fixture filter was too narrow

test-resolve-ktlo-epic watched two specific files:

      - 'test-fixtures/jira/setup_ktlo.py'
      - 'test-fixtures/jira/cleanup_ktlo.py'

but both of those import jira_client.py, and the job installs
test-fixtures/jira/requirements.txt. A change to either would not have rerun
it. Replaced with test-fixtures/jira/**.

Nothing caught this later either

test-all.yml runs only on push to master and on dispatch — there is no
pull_request trigger — so a PR editing shared/jira_common.py ran two suites
and the other six only broke after merge. It was also missing five suites
entirely, so master did not cover them either. All five are now wired in:

I did not add a pull_request trigger to test-all.yml. The path filters
are what the PR-time gap actually needed, and running all 22 suites on every PR
is a much bigger change than this ticket calls for.

One thing to decide before merging

test-resolve-ktlo-epic's integration-test hits the Jira sandbox and, unlike
test-jira-fixtures, it has no continue-on-error. Wiring it into
test-all.yml therefore creates a new way for master to go red on sandbox
flakiness rather than on a real regression. I have included it because leaving
suites out of "Test All Actions" is the gap being fixed, but it is a one-line
removal if you would rather not take that exposure — or a reason to give that
job the same continue-on-error treatment its sibling already has.

Verification

Checked mechanically rather than by eye, after the change:

• Every test-*.yml on disk is now referenced by test-all.yml (none missing).
• Every workflow test-all.yml calls declares workflow_call (none missing) —
  this is what caught test-bump-version.
• Every action whose Python imports jira_common/path_utils now has
  shared/** in both its pull_request and push filters.
• All test workflows still parse.

The one remaining gap is sonar-update-center-release: it imports shared/
and has no test workflow at all, so there is no trigger to fix. Out of scope
here, but worth a ticket.

🤖 Generated with Claude Code